docs(azure): Kimi-only crosscheck routing with visible fallback, and R10 Slack team exposure - #259

… degradation, stale claims

The review caught the requirement clause still saying bidirectionality while
the standing design is one-way into one outside family; the amendment and the
R6 title now state the actual requirement (no author reviewed by its own
family). The fallback path is recorded honestly: flipping to pi-codex includes
crosscheck-same-model on and accepts same-family review of codex-authored work
as a loud, recorded degradation, in the routing paragraph, the Work list, and
the acceptance. R5 now names the pi roster as the dormant fallback rather than
claiming crosscheck is done on it; C3 owns R10's per-submitter metering and
listener cost and its stale four-slots state line is refreshed to record the
2026-08-19 surrender cleanup; R10 uses the doc's status vocabulary.

… stale after the cleanup

The C3 state refresh left R4 still asserting one stranded work disk on the
subscription; that disk was deleted by owner direction on 2026-08-19 after no
cell record could be found for the sanctioned close. R4 now records the
deletion and that only the unfixed root cause remains. Also aligns the
amendment's requirement phrasing with R6's ('reviewed only by its own model
family') and rewraps two long lines.

…ne with the custody trade recorded

The owner revised the model pick from Kimi-K2.7-Code to GLM-5.2 on quality and
accepted the Fireworks custody shape after verification: Microsoft disclaims
data handling for the lane, the zero-data-retention promise is Fireworks' own
policy (volatile memory, no logging by default, chat completions only - the
Responses API and its 30-day store default are forbidden here), and billing
lands as Azure consumption with startup-credit coverage for pay-per-token Data
Zone Standard, to be confirmed by a small live decrement before volume. The
15-day retirement notice on Fireworks pay-per-token models is recorded as an
accepted operational risk and a standing reason the pi-codex fallback stays
armed. Work list gains the feature registration, the credit-decrement check,
the reasoning_effort passthrough smoke, and the chat-completions pin.

…it the C3 cleanup attribution